Upgrade to r110 #375
Closed
Upgrade to r110 #375
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ythreejs into fix/renderer_resize
Member
|
Great to see this happening. In we require 112. @mariobuikhuizen and I are not 100% if 110 would also do fine, but we could test that. Did you pick 110 for a particular reason? Mario told me that after 112 (so 113) there was a big change, so maybe 112 might also be easy. |
Contributor
Author
|
Closing in favor of #376. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR takes a stab at upgrading to r110. This should be is easier than upgrading right to r139.
Remaining autogen tasks: